System, method and article of manufacture for remote control and navigation of local content

ABSTRACT

A system, method and article of manufacture are provided for remotely controlling content stored on a local computer connected to a network system such as the Internet. The invention allows content such as DVD Video content to be locked so that play can only be accomplished through verification of user identity and also allows augmentation and supplementation of the content provided by the video from a remote server. In addition, upon verification of user client credentials, the present invention allows the locally stored content to be supplemented with additional content delivered over the network system. Furthermore, the present invention allows content stored locally on a client device to be remotely controlled to play synchronously on a plurality of client devices.

This application claims priority to U.S. patent application Ser. No.09/499,247, filed Feb. 7, 2000, of Getsin et al., for SYSTEM, METHOD ANDARTICLE OF MANUFACTURE FOR REMOTE CONTROL AND NAVIGATION OF LOCALCONTENT which U.S. patent application is fully incorporated herein byreference.

FIELD OF THE INVENTION

The present invention relates to remote control of content storedlocally on a client device such as a computer or set top box connectedto a network system, and more particularly to remote control of DVDVideo content on such a device.

BACKGROUND OF THE INVENTION

Multimedia computer systems have become increasingly popular over thelast several years due to their versatility and their interactivepresentation style. A multimedia computer system can be defined as acomputer system having a combination of video and audio outputs forpresentation of audio-visual displays. A modem multimedia computersystem typically includes one or more storage devices such as an opticaldrive, a CD-ROM, a hard drive, a videodisc, or an audiodisc, and audioand video data are typically stored on one or more of these mass storagedevices. In some file formats the audio and video are interleavedtogether in a single file, while in other formats the audio and videodata are stored in different files, many times on different storagemedia. Audio and video data for a multimedia display may also be storedin separate computer systems that are networked together. In thisinstance, the computer system presenting the multimedia display wouldreceive a portion of the necessary data from the other computer systemvia the network cabling.

Graphic images used in Windows multimedia applications can be created ineither of two ways, these being bit-mapped images and vector-basedimages. Bit-mapped images comprise a plurality of picture elements(pixels) and are created by assigning a color to each pixel inside theimage boundary. Most bit-mapped color images require one byte per pixelfor storage, so large bit-mapped images create correspondingly largefiles. For example, a full-screen, 256-color image in 640-by-480-pixelVGA mode requires 307,200 bytes of storage, if the data is notcompressed. Vector-based images are created by defining the end points,thickness, color, pattern and curvature of lines and solid objectscomprised within the image. Thus, a vector-based image includes adefinition which consists of a numerical representation of thecoordinates of the object, referenced to a corner of the image.

Bit-mapped images are the most prevalent type of image storage format,and the most common bit-mapped-image file formats are as follows. A fileformat referred to as BMP is used for Windows bit-map files in 1-, 2-,4-, 8-, and 24-bit color depths. BMP files contain a bit-map header thatdefines the size of the image, the number of color planes, the type ofcompression used (if any), and the palette used. The Windows DIB(device-independent bit-map) format is a variant of the BMP format thatincludes a color table defining the RGB (red green blue) values of thecolors used. Other types of bit-map formats include the TIF (taggedimage format file), the PCX (Zsoft Personal Computer Paintbrush Bitmap)file format, the GIF (graphics interchange file) format, and the TGA(Texas Instruments Graphic Architecture) file format.

The standard Windows format for bit-mapped images is a 256-colordevice-independent bit map (DIB) with a BMP (the Windows bit-mapped fileformat) or sometimes a DIB extension. The standard Windows format forvector-based images is referred to as WMF (Windows meta file).

Full-motion video implies that video images shown on the computer'sscreen simulate those of a television set with identical (30frames-per-second) frame rates, and that these images are accompanied byhigh-quality stereo sound. A large amount of storage is required forhigh-resolution color images, not to mention a full-motion videosequence. For example, a single frame of NTSC video at 640-by-400-pixelresolution with 16-bit color requires 512K of data per frame. At 30flames per second, over 15 Megabytes of data storage are required foreach second of full motion video. Due to the large amount of storagerequired for full motion video, various types of video compressionalgorithms are used to reduce the amount of necessary storage. Videocompression can be performed either in real-time, i.e., on the flyduring video capture, or on the stored video file after the video datahas been captured and stored on the media. In addition, different videocompression methods exist for still graphic images and for full-motionvideo.

Examples of video data compression for still graphic images are RLE(run-length encoding) and JPEG (Joint Photographic Experts Group)compression. RLE is the standard compression method for Windows BMP andDIB files. The RLE compression method operates by testing for duplicatedpixels in a single line of the bit map and stores the number ofconsecutive duplicate pixels rather than the data for the pixel itself.JPEG compression is a group of related standards that provide eitherlossless (no image quality degradation) or lossy (imperceptible tosevere degradation) compression types. Although JPEG compression wasdesigned for the compression of still images rather than video, severalmanufacturers supply JPEG compression adapter cards for motion videoapplications.

In contrast to compression algorithms for still images, most videocompression algorithms are designed to compress full motion video. Videocompression algorithms for motion video generally use a concept referredto as interframe compression, which involves storing only thedifferences between successive frames in the data file. Interframecompression begins by digitizing the entire image of a key frame.Successive frames are compared with the key frame, and only thedifferences between the digitized data from the key frame and from thesuccessive frames are stored. Periodically, such as when new scenes aredisplayed, new key frames are digitized and stored, and subsequentcomparisons begin from this new reference point. It is noted thatinterframe compression ratios are content-dependent, i.e., if the videoclip being compressed includes many abrupt scene transitions from oneimage to another, the compression is less efficient. Examples of videocompression which use an interframe compression technique are MPEG, DVIand Indeo, among others.

MPEG (Moving Pictures Experts Group) compression is a set of methods forcompression and decompression of full motion video images that uses theinterframe compression technique described above. The MPEG standardrequires that sound be recorded simultaneously with the video data, andthe video and audio data are interleaved in a single file to attempt tomaintain the video and audio synchronized during playback. The audiodata is typically compressed as well, and the MPEG standard specifies anaudio compression method referred to as ADPCM (Adaptive DifferentialPulse Code Modulation) for audio data.

A standard referred to as Digital Video Interactive (DVI) formatdeveloped by Intel Corporation is a compression and storage format forfull-motion video and high-fidelity audio data. The DVI standard usesinterframe compression techniques similar to that of the MPEG standardand uses ADPCM compression for audio data. The compression method usedin DVI is referred to as RTV 2.0 (real time video), and this compressionmethod is incorporated into Intel's AVK (audio/video kernel) softwarefor its DVI product line. IBM has adopted DVI as the standard fordisplaying video for its Ultimedia product line. The DVI file format isbased on the Intel i750 chipset and is supported through the MediaControl Interface (MCI) for Windows. Microsoft and Intel jointlyannounced the creation of the DV MCI (digital video media controlinterface) command set for Windows 3.1 in 1992.

The Microsoft Audio Video Interleaved (AVI) format is a specialcompressed file structure format designed to enable video images andsynchronized sound stored on CD-ROMs to be played on PCs with standardVGA displays and audio adapter cards. The AVI compression method uses aninterframe method, i.e., the differences between successive frames arestored in a manner similar to the compression methods used in DVI andMPEG. The AVI format uses symmetrical software compression-decompressiontechniques, i.e., both compression and decompression are performed inreal time. Thus AVI files can be created by recording video images andsound in AVI format from a VCR or television broadcast in real time, ifenough free hard disk space is available.

As discussed above, such audio and video content is often stored onmedia such as CD-ROM or digital video disc (DVD). However, once a vendorhas delivered such content to a customer, the vendor loses any practicalcontrol over the product. Even if the product is delivered under licenserather than out right sale, it has traditionally been difficult toprevent a customer from copying the content or providing the content toany number of friends so that they might illegally copy the content.

Another problem which arises from the vendors loss of control of thecontent maintenance and updating of the software. If content is to beadded or modified, the vendor must send a new disc to the customer. Inaddition, the vendor can not control the amount of data which thecustomer can access. In other words, once the disc is delivered, thecustomer will have access to all of the content on the disc and onlythat content. Time sensitive content, such as advertising, can becomeobsolete but will still be accessible on the disc.

Therefore, there remains a need for a system method or apparatusallowing flexible control of content delivered to a client. Such asystem, method or apparatus would preferably allow content to beinitially delivered on a traditional recording medium such as a CD-ROMor DVD but would allow a vendor to remote control the access of a userto the content stored thereon. Furthermore, such a system wouldpreferably allow a vendor supplement and/or modify the content and couldallow the vendor to limit a client's access to certain portions of thelocally stored content if desired. Furthermore, remote control ofnavigation would be preferably and could facilitate simultaneous accessby a controlled number of multiple clients if desired.

SUMMARY OF THE INVENTION

A system, method and article of manufacture are provided for remotelycontrolling local content for local access and use by a client device.An input is received from the client which can allow a transactionserver to identify the client. Once the client has been identified acommand can be sent to the client which controls the manner in which theclient device can use and access the local content.

The local content can be embodied on a digital video disk, and commandsgenerated by the transaction server can be in the form of an unlocksequence which allows the client device to access and use the contentstored on the disk. In addition, commands from the transaction servercan be used to navigate the content stored on the disk and can evensupplement the content stored thereon. The transaction server can, inresponse to a client identification, unlock content stored remotely onthe transaction server, allowing content to be easily maintained andupdated remotely at a single transaction site without having to replacemany DVD disks being used by many different clients.

In another embodiment of the invention, the present invention canremotely control synchronous play of the locally stored content at aplurality of client devices. This can be accomplished, for examplethrough use of a synchronization server used in conjunction with thetransaction server. Alternatively, the transaction server can performboth functions, that of a transaction server as well as that of asynchronization server.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood when consideration is given tothe following detailed description thereof. Such description makesreference to the annexed drawings wherein:

FIG. 1 is a schematic diagram of a hardware implementation of oneembodiment of the present invention;

FIG. 2 illustrates a flowchart delineating a method for synchronizing anevent on a plurality of client apparatuses in accordance with oneembodiment of the present invention;

FIG. 3 illustrates a flowchart delineating a method for storingsynchronization information for subsequent playback of an event inaccordance with one embodiment of the present invention;

FIG. 4 illustrates a flowchart setting forth a method for providingoverlays during a synchronized event on a plurality of clientapparatuses in accordance with one embodiment of the present invention;

FIG. 5 illustrates a flow diagram for delayed synchronization of anevent on a plurality of client apparatuses in accordance with oneembodiment of the present invention;

FIG. 6 illustrates a flow diagram for providing information on asynchronized event on a plurality of client apparatuses in accordancewith one embodiment of the present invention;

FIG. 7 illustrates a method for creating a synchronizer object in orderto playback an event simultaneously on a plurality of client apparatusesin accordance with one embodiment of the present invention;

FIG. 8 illustrates a flowchart for affording a scheduler object adaptedto facilitate the playback of an event simultaneously on a plurality ofnetworked client apparatuses in accordance with one embodiment of thepresent invention;

FIG. 9 is a flowchart delineating a method for identifying a pluralityof events which are played back simultaneously on a plurality ofnetworked client apparatuses in accordance with one embodiment of thepresent invention;

FIG. 10 shows a flowchart delineating a technique for interfacing aplurality of different types of playback devices of client apparatuseswhich are networked to simultaneously playback an event in accordancewith one embodiment of the present invention;

FIG. 11 illustrates the manner in which a layer factory is created inaccordance with one embodiment of the present invention;

FIG. 12 illustrates the manner in which user requests are processed inaccordance with one embodiment of the present invention;

FIGS. 13-16 illustrate various class/component diagrams in accordancewith one embodiment of the present invention;

FIG. 17 illustrates a logical sequence diagram in accordance with oneembodiment of the present invention;

FIG. 18 illustrates a logical sequence diagram that shows server sidecollaboration in accordance with one embodiment of the presentinvention;

FIG. 19 illustrates a logical sequence diagram showing client sidecollaboration in accordance with one embodiment of the presentinvention;

FIG. 20 is a schematic diagram of a process according to an embodimentof the present invention;

FIG. 21 is a schematic diagram illustrating an embodiment of the presentinvention;

FIG. 22 is a schematic diagram illustrating another embodiment of thepresent invention;

FIG. 23 is a schematic diagram illustrating yet another embodiment ofthe present invention;

FIG. 24 is a schematic diagram illustrating still another embodiment ofthe present inveniton;

FIG. 25 is a flowchart illustrating a method for carrying out thepresent invention;

FIG. 26 is a flowchart illustrating a method for carrying out an aspectof the present inveniton; and

FIG. 27 is a flowchart illustrating one embodiment of steps carried outby a server when remotely unlocking local content.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIGS. 1-26 illustrate a system for remotely controlling content storedlocally on a client apparatus. Prior to use, an event is stored inmemory on at least one client apparatuse. Such client apparatus isadapted to be connected to a network along with a host computer(s). Inoperation, information is transmitted from the host computer to the atleast one client apparatus utilizing the network. This informationcontrols playback of the event stored on locally on the client computer.

In various embodiments, the client apparatus may take the form of acomputer, television, stereo, home appliance, or any other types ofdevices. In one embodiment, the client apparatuses and the host computereach include a computer such as an IBM compatible computer, AppleMacintosh computer or UNIX based workstation.

A representative hardware environment is depicted in FIG. 1, whichillustrates a typical hardware configuration of a workstation inaccordance with a preferred embodiment having a central processing unit110, such as a microprocessor, and a number of other unitsinterconnected via a system bus 112. The workstation shown in FIG. 1includes a Random Access Memory (RAM) 114, Read Only Memory (ROM) 116,an I/O adapter 118 for connecting peripheral devices such as diskstorage units 120 (i.e. DVD playback device) to the bus 112, a userinterface adapter 122 for connecting a keyboard 124, a mouse 126, aspeaker 128, a microphone 132, and/or other user interface devices suchas a touch screen (not shown) to the bus 112, communication adapter 134for connecting the workstation to a communication network (e.g., a dataprocessing network) and a display adapter 136 for connecting the bus 112to a display device 138. The workstation typically has resident thereonan operating system such as the Microsoft Windows NT or Windows/95Operating System (OS), the IBM OS/2 operating system, the MAC OS, orUNIX operating system. Those skilled in the art will appreciate that thepresent invention may also be implemented on platforms and operatingsystems other than those mentioned.

A preferred embodiment is written using JAVA, C, and the C++ languageand utilizes object oriented programming methodology. Object orientedprogramming (OOP) has become increasingly used to develop complexapplications. As OOP moves toward the mainstream of software design anddevelopment, various software solutions require adaptation to make useof the benefits of OOP. A need exists for these principles of OOP to beapplied to a messaging interface of an electronic messaging system suchthat a set of OOP classes and objects for the messaging interface can beprovided.

OOP is a process of developing computer software using objects,including the steps of analyzing the problem, designing the system, andconstructing the program. An object is a software package that containsboth data and a collection of related structures and procedures. Sinceit contains both data and a collection of structures and procedures, itcan be visualized as a self-sufficient component that does not requireother additional structures, procedures or data to perform its specifictask. OOP, therefore, views a computer program as a collection oflargely autonomous components, called objects, each of which isresponsible for a specific task. This concept of packaging data,structures, and procedures together in one component or module is calledencapsulation.

In general, OOP components are reusable software modules which presentan interface that conforms to an object model and which are accessed atrun-time through a component integration architecture. A componentintegration architecture is a set of architecture mechanisms which allowsoftware modules in different process spaces to utilize each others'capabilities or functions. This is generally done by assuming a commoncomponent object model on which to build the architecture. It isworthwhile to differentiate between an object and a class of objects atthis point. An object is a single instance of the class of objects,which is often just called a class. A class of objects can be viewed asa blueprint, from which many objects can be formed.

OOP allows the programmer to create an object that is a part of anotherobject. For example, the object representing a piston engine is said tohave a composition-relationship with the object representing a piston.In reality, a piston engine comprises a piston, valves and many othercomponents; the fact that a piston is an element of a piston engine canbe logically and semantically represented in OOP by two objects.

OOP also allows creation of an object that “depends from” anotherobject. If there are two objects, one representing a piston engine andthe other representing a piston engine wherein the piston is made ofceramic, then the relationship between the two objects is not that ofcomposition. A ceramic piston engine does not make up a piston engine.Rather it is merely one kind of piston engine that has one morelimitation than the piston engine; its piston is made of ceramic. Inthis case, the object representing the ceramic piston engine is called aderived object, and it inherits all of the aspects of the objectrepresenting the piston engine and adds further limitation or detail toit. The object representing the ceramic piston engine “depends from” theobject representing the piston engine. The relationship between theseobjects is called inheritance.

When the object or class representing the ceramic piston engine inheritsall of the aspects of the objects representing the piston engine, itinherits the thermal characteristics of a standard piston defined in thepiston engine class. However, the ceramic piston engine object overridesthese ceramic specific thermal characteristics, which are typicallydifferent from those associated with a metal piston. It skips over theoriginal and uses new functions related to ceramic pistons. Differentkinds of piston engines have different characteristics, but may have thesame underlying functions associated with it (e.g., how many pistons inthe engine, ignition sequences, lubrication, etc.). To access each ofthese functions in any piston engine object, a programmer would call thesame functions with the same names, but each type of piston engine mayhave different/overriding implementations of functions behind the samename. This ability to hide different implementations of a functionbehind the same name is called polymorphism and it greatly simplifiescommunication among objects.

With the concepts of composition-relationship, encapsulation,inheritance and polymorphism, an object can represent just aboutanything in the real world. In fact, one's logical perception of thereality is the only limit on determining the kinds of things that canbecome objects in object-oriented software. Some typical categories areas follows:

-   -   Objects can represent physical objects, such as automobiles in a        traffic-flow simulation, electrical components in a        circuit-design program, countries in an economics model, or        aircraft in an air-traffic-control system.    -   Objects can represent elements of the computer-user environment        such as windows, menus or graphics objects.    -   An object can represent an inventory, such as a personnel file        or a table of the latitudes and longitudes of cities.    -   An object can represent user-defined data types such as time,        angles, and complex numbers, or points on the plane.

With this enormous capability of an object to represent just about anylogically separable matters, OOP allows the software developer to designand implement a computer program that is a model of some aspects ofreality, whether that reality is a physical entity, a process, a system,or a composition of matter. Since the object can represent anything, thesoftware developer can create an object which can be used as a componentin a larger software project in the future.

If 90% of a new OOP software program consists of proven, existingcomponents made from preexisting reusable objects, then only theremaining 10% of the new software project has to be written and testedfrom scratch. Since 90% already came from an inventory of extensivelytested reusable objects, the potential domain from which an error couldoriginate is 10% of the program. As a result, OOP enables softwaredevelopers to build objects out of other, previously built objects.

This process closely resembles complex machinery being built out ofassemblies and sub-assemblies. OOP technology, therefore, makes softwareengineering more like hardware engineering in that software is builtfrom existing components, which are available to the developer asobjects. All this adds up to an improved quality of the software as wellas an increased speed of its development.

Programming languages are beginning to fully support the OOP principles,such as encapsulation, inheritance, polymorphism, andcomposition-relationship. With the advent of the C++ language, manycommercial software developers have embraced OOP. C++ is an OOP languagethat offers a fast, machine-executable code. Furthermore, C++ issuitable for both commercial-application and systems-programmingprojects. For now, C++ appears to be the most popular choice among manyOOP programmers, but there is a host of other OOP languages, such asSmalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally,OOP capabilities are being added to more traditional popular computerprogramming languages such as Pascal.

The benefits of object classes can be summarized, as follows:

-   -   Objects and their corresponding classes break down complex        programming problems into many smaller, simpler problems.    -   Encapsulation enforces data abstraction through the organization        of data into small, independent objects that can communicate        with each other. Encapsulation protects the data in an object        from accidental damage, but allows other objects to interact        with that data by calling the object's member functions and        structures.    -   Subclassing and inheritance make it possible to extend and        modify objects through deriving new kinds of objects from the        standard classes available in the system. Thus, new capabilities        are created without having to start from scratch.    -   Polymorphism and multiple inheritance make it possible for        different programmers to mix and match characteristics of many        different classes and create specialized objects that can still        work with related objects in predictable ways.    -   Class hierarchies and containment hierarchies provide a flexible        mechanism for modeling real-world objects and the relationships        among them.    -   Libraries of reusable classes are useful in many situations, but        they also have some limitations. For example:    -   Complexity. In a complex system, the class hierarchies for        related classes can become extremely confusing, with many dozens        or even hundreds of classes.    -   Flow of control. A program written with the aid of class        libraries is still responsible for the flow of control (i.e., it        must control the interactions among all the objects created from        a particular library). The programmer has to decide which        functions to call at what times for which kinds of objects.    -   Duplication of effort. Although class libraries allow        programmers to use and reuse many small pieces of code, each        programmer puts those pieces together in a different way. Two        different programmers can use the same set of class libraries to        write two programs that do exactly the same thing but whose        internal structure (i.e., design) may be quite different,        depending on hundreds of small decisions each programmer makes        along the way. Inevitably, similar pieces of code end up doing        similar things in slightly different ways and do not work as        well together as they should.

Class libraries are very flexible. As programs grow more complex, moreprogrammers are forced to reinvent basic solutions to basic problemsover and over again. A relatively new extension of the class libraryconcept is to have a framework of class libraries. This framework ismore complex and consists of significant collections of collaboratingclasses that capture both the small scale patterns and major mechanismsthat implement the common requirements and design in a specificapplication domain. They were first developed to free applicationprogrammers from the chores involved in displaying menus, windows,dialog boxes, and other standard user interface elements for personalcomputers.

Frameworks also represent a change in the way programmers think aboutthe interaction between the code they write and code written by others.In the early days of procedural programming, the programmer calledlibraries provided by the operating system to perform certain tasks, butbasically the program executed down the page from start to finish, andthe programmer was solely responsible for the flow of control. This wasappropriate for printing out paychecks, calculating a mathematicaltable, or solving other problems with a program that executed in justone way.

The development of graphical user interfaces began to turn thisprocedural programming arrangement inside out. These interfaces allowthe user, rather than program logic, to drive the program and decidewhen certain actions should be performed. Today, most personal computersoftware accomplishes this by means of an event loop which monitors themouse, keyboard, and other sources of external events and calls theappropriate parts of the programmer's code according to actions that theuser performs. The programmer no longer determines the order in whichevents occur. Instead, a program is divided into separate pieces thatare called at unpredictable times and in an unpredictable order. Byrelinquishing control in this way to users, the developer creates aprogram that is much easier to use. Nevertheless, individual pieces ofthe program written by the developer still call libraries provided bythe operating system to accomplish certain tasks, and the programmermust still determine the flow of control within each piece after it'scalled by the event loop. Application code still “sits on top of” thesystem.

Even event loop programs require programmers to write a lot of code thatshould not need to be written separately for every application. Theconcept of an application framework carries the event loop conceptfurther. Instead of dealing with all the nuts and bolts of constructingbasic menus, windows, and dialog boxes and then making these things allwork together, programmers using application frameworks start withworking application code and basic user interface elements in place.Subsequently, they build from there by replacing some of the genericcapabilities of the framework with the specific capabilities of theintended application.

Application frameworks reduce the total amount of code that a programmerhas to write from scratch. However, because the framework is really ageneric application that displays windows, supports copy and paste, andso on, the programmer can also relinquish control to a greater degreethan event loop programs permit. The framework code takes care of almostall event handling and flow of control, and the programmer's code iscalled only when the framework needs it (e.g., to create or manipulate aproprietary data structure).

A programmer writing a framework program not only relinquishes controlto the user (as is also true for event loop programs), but alsorelinquishes the detailed flow of control within the program to theframework. This approach allows the creation of more complex systemsthat work together in interesting ways, as opposed to isolated programs,having custom code, being created over and over again for similarproblems.

Thus, as is explained above, a framework basically is a collection ofcooperating classes that make up a reusable design solution for a givenproblem domain. It typically includes objects that provide defaultbehavior (e.g., for menus and windows), and programmers use it byinheriting some of that default behavior and overriding other behaviorso that the framework calls application code at the appropriate times.

There are three main differences between frameworks and class libraries:

-   -   Behavior versus protocol. Class libraries are essentially        collections of behaviors that you can call when you want those        individual behaviors in your program. A framework, on the other        hand, provides not only behavior but also the protocol or set of        rules that govern the ways in which behaviors can be combined,        including rules for what a programmer is supposed to provide        versus what the framework provides.    -   Call versus override. With a class library, the code the        programmer instantiates objects and calls their member        functions. It's possible to instantiate and call objects in the        same way with a framework (i.e., to treat the framework as a        class library), but to take full advantage of a framework's        reusable design, a programmer typically writes code that        overrides and is called by the framework. The framework manages        the flow of control among its objects. Writing a program        involves dividing responsibilities among the various pieces of        software that are called by the framework rather than specifying        how the different pieces should work together.    -   Implementation versus design. With class libraries, programmers        reuse only implementations, whereas with frameworks, they reuse        design. A framework embodies the way a family of related        programs or pieces of software work. It represents a generic        design solution that can be adapted to a variety of specific        problems in a given domain. For example, a single framework can        embody the way a user interface works, even though two different        user interfaces created with the same framework might solve        quite different interface problems.

Thus, through the development of frameworks for solutions to variousproblems and programming tasks, significant reductions in the design anddevelopment effort for software can be achieved. A preferred embodimentof the invention utilizes HyperText Markup Language (HTML) to implementdocuments on the Internet together with a general-purpose securecommunication protocol for a transport medium between the client and theNewco. HTTP or other protocols could be readily substituted for HTMLwithout undue experimentation. Information on these products isavailable in T. Berners-Lee, D. Connoly, “RFC 1866: Hypertext MarkupLanguage—2.0” (November 1995); and R. Fielding, H, Frystyk, T.Berners-Lee, J. Gettys and J. C. Mogul, “Hypertext TransferProtocol—HTTP/1.1: HTTP Working Group Internet Draft” (May 2, 1996).HTML is a simple data format used to create hypertext documents that areportable from one platform to another. HTML documents are SGML documentswith generic semantics that are appropriate for representing informationfrom a wide range of domains. HTML has been in use by the World-Wide Webglobal information initiative since 1990. HTML is an application of ISOStandard 8879; 1986 Information Processing Text and Office Systems;Standard Generalized Markup Language (SGML).

To date, Web development tools have been limited in their ability tocreate dynamic Web applications which span from client to server andinteroperate with existing computing resources. Until recently, HTML hasbeen the dominant technology used in development of Web-based solutions.However, HTML has proven to be inadequate in the following areas:

-   -   Poor performance;    -   Restricted user interface capabilities;    -   Can only produce static Web pages;    -   Lack of interoperability with existing applications and data;        and    -   Inability to scale.

Sun Microsystem's Java language solves many of the client-side problemsby:

-   -   Improving performance on the client side;    -   Enabling the creation of dynamic, real-time Web applications;        and    -   Providing the ability to create a wide variety of user interface        components.

With Java, developers can create robust User Interface (UI) components.Custom “widgets” (e.g., real-time stock tickers, animated icons, etc.)can be created, and client-side performance is improved. Unlike HTML,Java supports the notion of client-side validation, offloadingappropriate processing onto the client for improved performance.Dynamic, real-time Web pages can be created. Using the above-mentionedcustom UI components, dynamic Web pages can also be created.

Sun's Java language has emerged as an industry-recognized language for“programming the Internet.” Sun defines Java as: “a simple,object-oriented, distributed, interpreted, robust, secure,architecture-neutral, portable, high-performance, multithreaded,dynamic, buzzword-compliant, general-purpose programming language. Javasupports programming for the Internet in the form ofplatform-independent Java applets.” Java applets are small, specializedapplications that comply with Sun's Java Application ProgrammingInterface (API) allowing developers to add “interactive content” to Webdocuments (e.g., simple animations, page adornments, basic games, etc.).Applets execute within a Java-compatible browser (e.g., NetscapeNavigator) by copying code from the server to client. From a languagestandpoint, Java's core feature set is based on C++. Sun's Javaliterature states that Java is basically, “C++ with extensions fromObjective C for more dynamic method resolution.”

Another technology that provides similar function to JAVA is provided byMicrosoft and ActiveX Technologies, to give developers and Web designerswherewithal to build dynamic content for the Internet and personalcomputers. ActiveX includes tools for developing animation, 3-D virtualreality, video and other multimedia content. The tools use Internetstandards, work on multiple platforms, and are being supported by over100 companies. The group's building blocks are called ActiveX Controls,small, fast components that enable developers to embed parts of softwarein hypertext markup language (HTML) pages. ActiveX Controls work with avariety of programming languages including Microsoft Visual C++, BorlandDelphi, Microsoft Visual Basic programming system and, in the future,Microsoft's development tool for Java, code named “Jakarta.” ActiveXTechnologies also includes ActiveX Server Framework, allowing developersto create server applications. One of ordinary skill in the art readilyrecognizes that ActiveX could be substituted for JAVA without undueexperimentation to practice the invention.

Synchronization Overview

FIG. 2 illustrates a flowchart delineating a method for synchronizing anevent on a plurality of client apparatuses. First, in operation 200, anevent is stored in memory on at least one of the client apparatuses. Invarious embodiments, the memory may take the form of an electromagneticmedium, or any type of optical storage device, i.e. CD-audio. In aprimary aspect of the present invention, the memory includes a digitalvideo disc (DVD) (audio or video). Further, for reasons that will soonbecome apparent, the information includes chapter information associatedwith the DVD. In such embodiment where the memory is portable, the usermay be required to purchase the memory, i.e. DVD, in order toparticipate in a synchronized event, thus increasing the sale of DVD's.

It should be noted that the event need not be necessarily stored inmemory on all of the client apparatuses, but rather stored on one orsome of the client apparatuses and streamed to the remaining clientapparatuses at variant rates. This may be feasibly accomplished if theclient apparatus(es) containing the stored event has a high-bandwidthconnection with the remaining client apparatuses. For example, theclient apparatus(es) containing the stored event may include a serverthat has a connection to a plurality of televisions via a cable network,i.e. WEBTV. Similar functionality may be achieved via a broadcastmedium. The present invention is thus flexible by having an ability tohost user events and corporative events.

In one embodiment, the event includes a video and audio presentationsuch as movie, a concert, and/or a theatrical event. It should be noted,however, that the event may included any recording capable of beingplayed back for entertainment, education, informative or other similarpurposes.

In use, the client apparatuses and a host computer are adapted to beconnected to a network. Such network may include a wide, local or anyother type of communication network. For example, a wide area networksuch as the Internet may be employed which operates using TCP/IP or IPXprotocols.

In operation 202, information is transmitted from the host computer tothe appropriate client apparatuses utilizing the network. Thisinformation allows for the simultaneous and synchronous playback of theevent on each of the client apparatuses. In one embodiment, theinformation may also include a start time when the playback of the eventis to begin on each of the client apparatuses. Further, an ending timemay be included when the playback of the event is to end on each of theclient apparatuses. Still yet, “play” command information may be sent tothe client apparatuses at the start time. As an option, input may bereceived from the user, and used to alter the playback of the event. Thehost server, or synchronization server, can also control various streamsof a variant rate and different hardware associated with those streams.

The present invention thus has the ability to synchronize video playbackfor one or multiple (thousands) users from one or multiple physicallocations, and to synchronize with external video, audio and/or datastreams.

Users of the present invention are at multiple physical locations andhost servers may also be at different locations. The present inventionis thus a scalable system which is capable of servicing an unlimitednumber of users. Since the content is local to the user machine, no highnetwork bandwidth is required.

History Download Capabilities

FIG. 3 illustrates a flowchart delineating a method for storingsynchronization information for subsequent playback of an event.Initially, in operation 300, an event is stored in memory on at leastone of the client apparatuses, as set forth earlier. These clientapparatuses are adapted to be connected to a network along with a hostcomputer during use.

In operation 302, information is stored on the host computer(s) forallowing the simultaneous playback of the event on each of the clientapparatuses. In one embodiment, the information may include a historyand data associated with the synchronous playback. In particular, thehistory may include any overlaid material(as will be describedhereinafter in greater detail), any specific commands affecting theplayback of the information, or any other type of general information,i.e. start time, end time, etc.

In operation 304, the information may be downloaded utilizing thenetwork at any time after the synchronous playback of the event. Suchdownloaded information may then be used for playback after thesimultaneous playback of the event. As such, the present invention hasthe ability to allow users to download a history and data associatedwith a particular synchronization event and play it later.

Overlay Synchronization

FIG. 4 illustrates a flowchart setting forth a method for providingoverlays during a synchronized event on a plurality of clientapparatuses or any other source. First, in operation 400, a plurality ofclient apparatuses are connected via a network. In operation 402, anevent may be simultaneously played back on the client apparatusesutilizing the network, as set forth earlier.

During the playback of the event, visual and/or audio material may alsobe overlaid on the event based on input received from at least one ofthe client apparatuses. See operation 404. This may be accomplished bytransmitting the overlay material from one of the client apparatuses tothe host computer or any other server, and multicasting the same to theremaining client apparatuses.

As an option, the overlay material may include annotations on a displayof the client apparatus. For example, the overlay material may includesketches which are inputted by way of a stylus-based input screen or akeyboard or the like, along with a voiceover inputted by way of amicrophone or voice synthesizer. Such capability may also be quitevaluable in an educational environment.

In one embodiment, the overlay material may also be displayed on each ofthe client apparatuses utilizing the network. This allows each of theusers to experience the overlay in real-time during the simultaneousplayback of the event. As an option, the user inputting the overlaymaterial may select which users may experience the overlay material. Theclient apparatus that provided the overlay material may also beidentified to the users experiencing the overlay material.

It should be noted that various bi-directional communication may beenabled for allowing data to travel to and from the server. Forinstance, the playback of the event on the client apparatuses may bealtered in any feasible way based on input from a user.

Late Synchronization

FIG. 5 illustrates a flow diagram for delayed synchronization of anevent on a plurality of client apparatuses. First, in operation 500, aplurality of client apparatuses are connected via a network and an eventis stored in memory on the client apparatuses. The event is thensimultaneously played back on the client apparatuses utilizing thenetwork, as set forth earlier. Note operation 502.

During the simultaneous playback, a request may be received from one ofthe client apparatuses for that particular to be included in thesynchronized event, as set forth in operation 504. This request may bereceived after the synchronized event has already begun while it isstill playing. Further, the request may be submitted via a site on anetwork, i.e. website.

In response to the request, information is transmitted in operation 506to the requesting client apparatus utilizing the network. Thisinformation is adapted for identifying a location in the memory wherethe event is currently being played back. This allows the simultaneousplayback of the event on the requesting client apparatus.

The end users are thus able to come in at a later time and to besynchronized with the event. Targeted synchronization and variousfilters criteria can be applied to target different audiences. Alsolanguage and cultural differences can be taken into account. Still yet,the present invention may be adapted to address users on differenthardware platforms (MAC, PC, set-top boxes). This may be accomplished byidentifying the user using a cookie, a user profile which is identifiedby way of a log in, or a Bum Cut Area (BCA) of the disc.

An example setting forth details relating to identifying DVDs will nowbe set forth. First, a content owner (such as studio) requests use ofthe BCA on their DVDs. Based on request, the replicator (examplesinclude WAMO, Panasonic, Nimbus, Technicolor, Pioneer, Crest) addsunique BCA number to every DVD. Adding BCA number to each DVD requires aspecial (YAG) laser. This may be the very last step in the manufacturingprocess. The BCA numbers for a specific DVD must then be entered intoInterActual's BCA database. Information to track includes: DVD title,i.e. “Lost in Space”; BCA #/range, i.e. 12345687890; and ShippingPackaging/Tracking Container, i.e. Box 52221 to Hollywood Video.

After the BCA number is added to the DVDs, the DVDs are packaging/boxedfor distribution to either the Distributor or the Retailer. It should benoted that many companies take multiple forms, so the replicator anddistributor may be one in the same. Also, some retailers arelarge/important enough to get shipments directly from replicator. Theway in which the DVDs are packaging/shipped is very important becauseone must track the BCA numbers to actual shipping containers (box,etc.). Therefore tracking information must also be added to the BCAdatabase.

If packaged DVDs are then sent to distributor, the distributor also hasmechanisms, i.e. scanners, input device, and monitoring devices, inplace for tracking based on their distribution. For example, Deluxe mayreceive a “package” of 100,000 copies of “Lost in Space.” However, thedistributor ships 10,000 to Retailer A and 5,000 to Retailer B. Thedistributor should be able to “input” retailer A and B's distributioninformation into the system. Ideally, this becomes a seamless/automatedprocess. Once the DVDs reach the retailer (either from the replicator ordistributor), then DVDs may be further divided and distributed to localstores/outlets. In such a situation, the retailer should be able toautomatically “track” distribution of these DVDs through to theirstores. Over time, all three entitities (replicator, distributor, andretailer) are able to add tracking information to BCA database. Due tocomplexity and dependencies on existing business systems, the retailtracking concept will be rolled out in phases: replicator first mostlikely with key retail accounts. The distributors will be brought in.Retailers will then begin to embrace the ability to track based on localoutlet/store.

By the foregoing design, easy deployment is thus afforded and minimalhardware is required to allow the synchronization of content withoutsignificant capital investments and with a very efficient controlmechanism. The content delivery does not rely on high network bandwidthand is independent from the synchronization.

Internet Server Application Program Interface (ISAPI) extensions will beused on the server. ISAPI extensions provide a mechanism to maintain atemporary or permanent connection with the users. These connectionsallow the Synchronization Server to process request and to send theappropriate DVD commands. The permanent connections are known as “KeepAlive” connections. ISAPI extension can also be used as an HTTPinterface to a more traditional server, with all data returned as text.

On the client side the approach is to use, but not limited to Java 1.1applets, to initiate event start-up for the Synchronization server. Theadvantage of using Java 1.1 applets is to achieve platform independencefor existing and future Java-enabled devices. JavaScript will be used toprovide user interface navigation by “wrapping” the applet.

An ISAPI (Internet Server Application Program Interface) is a set ofWindows program calls that let one write a Web server application thatwill run faster than a Common Gateway Interface (CGI) application. Adisadvantage of a CGI application (or “executable file,” as it issometimes called) is that each time it is run, it runs as a separateprocess with its own address space, resulting in extra instructions thathave to be performed, especially if many instances of it are running onbehalf of users. Using ISAPI, you create a Dynamic Link Library (DLL)application file that can run as part of the Hypertext TransportProtocol (HTTP) application's process and address space. The DLL filesare loaded into the computer when HTTP is started and remain there aslong as they are needed; they don't have to be located and read intostorage as frequently as a CGI application.

Existing CGI applications can be converted into ISAPI application DLLswithout having to rewrite their logic. However, they do need to bewritten to be thread-safe so that a single instance of the DLL can servemultiple users.

A special kind of ISAPI DLL is called an ISAPI filter, which can bedesignated to receive control for every HTTP request. One can create anISAPI filter for encryption or decryption, for logging, for requestscreening, or for other purposes.

One can write ISAPI server extension DLLs (ISAS) that can be loaded andcalled by the HTTP server. Users can fill out forms and click a submitbutton to send data to a Web server and invoke an ISA, which can processthe information to provide custom content or store it in a database. Webserver extensions can use information in a database to build Web pagesdynamically, and then send them to the client computers to be displayed.An application can add other custom functionality and provide data tothe client using HTTP and HTML.

One can write an ISAPI filter. The filter is also a DLL that runs on anISAPI-enabled HTTP server. The filter registers for notification ofevents such as logging on or URL mapping. When the selected eventsoccur, the filter is called, and one can monitor and change the data (onits way from the server to the client or vice versa). ISAPI filters canbe used to provide custom encryption or compression schemes, oradditional authentication methods.

Both server extensions and filters run in the process space of the Webserver, providing an efficient way to extend the server's capabilities.

Overall Component Design

The various functional components of the software associated with thepresent invention will now be set forth. Such components include aJava/JavaScript Component, Synchronizer Component, LayerImpl Component,Business Layer Component, Configuration Manager Component, and DBConnectComponent.

Java/JavaScript Component

FIG. 6 illustrates a flow diagram for providing information on asynchronized event on a plurality of client apparatuses in accordancewith one embodiment of the present invention. First, in operation 600, aplurality of client apparatuses are connected via a network, as setforth earlier. Next, an application program is embedded on a site on thenetwork in operation 602. Such application program may take the form ofa JAVA applet, and the site may include a website on the Internet.

In use, information is requested from a server on the network utilizingthe application program. See operation 604. Such information relates toan event to be played back simultaneously on the client apparatuses andmay include general information such as a start and stop time of theevent, or more specific information about the event itself.

In response to such request, a script is received for displaying theinformation. Note operation 606. The script may take any form such asPerl, REXX (on IBM mainframes), and Tcl/Tk, and preferably includes aJAVAscript.

In one embodiment of the present invention, the JAVA applet may befurther adapted to send a request to retrieve command information fromthe server for use with a playback device of one of the clientapparatuses. The commands may be adapted to playback the event on theplayback device simultaneous with the playback of the event on theremaining client apparatuses. Further, the commands may include a starttime when the playback of the event is to begin on each of the clientapparatuses.

The JAVA applets and JAVAscript are used to communicate with theplayback device of the client apparatuses. In one embodiment, theplayback device includes a PCFriendly TM video player manufactured byInteractual®.

The Java applet is embedded within a web page and uses HTTP protocol tocommunicate to the synchronization server. The applet could requestevent information from the server, and display it to the user viaJavaScript. The applet could also send a “BroadcastVideoEvent” requestto retrieve DVD commands that can be passed to the video component, asset forth hereinabove.

Synchronizer Component

FIG. 7 illustrates a method for creating a synchronizer object in orderto playback an event simultaneously on a plurality of clientapparatuses. The synchronizer object is portion of the software thatactually implements the synchronization procedure. First, in operation700, a request is received utilizing a network for viewing an event.Next, the request is queued in memory in operation 702.

In response to the request, in operation 704, an object is created whichis adapted to playback the event on a client apparatus simultaneous withthe playback of the event on the remaining client apparatuses upon thereceipt of an activation signal. As an option, the activation signal maybe provided using a clock of the client apparatus, or located at adifferent location, i.e. server. To accomplish this, the objectidentifies a start time when the playback of the event is to begin oneach of the client apparatuses.

In operation 706, the object is sent to one of the client apparatusesutilizing the network for being stored therein. In accordance with aprimary aspect of the present invention, the object may be adapted toplayback the event which is stored in memory of the client apparatus.This may be accomplished by activating a digital video disc (DVD)player.

In summary, when the Synchronizer component receives a“BroadcastVideoEvent” from the applet, it then places the request in thethread queue for processing. To process a request, the thread creates a“call back” object, if one does not exist for this event. The threadthen adds the request to the “call back” object queue. This “call back”object will be invoked when it is time to play the DVD. The Synchronizercomponent creates a Call Back COM object, LayerSink. The Synchronizercomponent is also responsible for creating the LayerFactory interfacewhich will be set forth hereinafter in greater detail.

LayerImpl Component

FIG. 8 illustrates a flowchart for affording a scheduler object adaptedto facilitate the playback of an event simultaneously on a plurality ofnetworked client apparatuses. The present method ensures that criticalinformation is tracked during the synchronization of the event. Suchcritical information not only ensures proper synchronization, but alsoenables various peripheral features.

First, in operation 800, various values are determined including acurrent time, a start time when an event is to start, and a stop timewhen the event is to end. Thereafter, a length of the event iscalculated based on the start time and the stop time in operation 802.As an option, the current time is determined by querying a clock of oneof the client apparatuses.

If any portion of the length of the event takes place during apredetermined threshold period, a command is stored in memory inoperation 804. The command may be adapted to automatically begin playingback the event at the start time. In one embodiment, the thresholdperiod includes the time the users can be queued before the event. As anoption, chapter information may be stored in the memory if any portionof the length of the event takes place during the predeterminedthreshold period. This allows the command to automatically begin playingback the event at a predetermined chapter.

In operation 806, a loop is created at the start time during which alapsed time of the event is tracked. This information may be used forvarious tracking purposes to decide when to issue commands to the user.In another embodiment, a second loop may be created upon the beginningof a chapter during which information on a next chapter is retrieved.

The “call back” object (LayerSink) is thus responsible for creating andcommunicating with the LayerImpl component. The LayerImpl component actsas a scheduler, determining when to issue commands to the user.

LayerImpl will issue different DVD commands, based on the type ofdecoder the user has in their PC. LayerImpl will differentiate betweenthe decoders by using the decoder information submitted from the client.The LayerImpl will pass the correct DVD command to the client, based onthe decoder's capabilities. For example, if the decoder does not supportthe TimePlay event, then the server may send a ChapterPlay event andwait appropriately.

The following is an enumerated summary of the steps the component usesto determine when the users will receive the DVD commands:

1. Retrieves the current time, and the time the event starts and ends.

2. Calculates the length of the event.

3. If the event is within a threshold period (i.e. the time users can bequeued before the event), then store the first DVD command in memory.Also, store the Chapter information in memory.

4. Create a loop that processes request until the event has completed.

5. In the loop, calculate the lapsed time of the event.

6. In the loop, retrieve the next chapter information.

7. Create another loop that will loop until time for the next chapter tobe played.

8. When the next chapter is ready to play, send the command that wasretrieved from the Chapter table.

Business Layer Component

FIG. 9 is a flowchart delineating a method for identifying a pluralityof events which are played back simultaneously on a plurality ofnetworked client apparatuses. This features is important since a hostserver may be synchronizing more than one event at once, or duringoverlapping times. Such events must therefore be distinguished.

First, in operation 900, a plurality of events are stored in memory on aplurality of client apparatuses. Each of the events is assigned a uniqueidentifier which is stored in the memory.

In operation 902, the client apparatuses are adapted to be coupled to ahost computer via a network, as set forth hereinabove. In operation 904,the identifier of the event which is stored in the memory of the clientapparatuses is then retrieved utilizing the network. Such identifier issubsequently compared with an identifier of a scheduled event, as setforth in operation 906. If the comparison renders a match, the playbackof the event is begun on the appropriate client apparatuses. Noteoperation 908.

CbusinessLayer thus differentiates events by the disk and location ids,uploaded by the client to guarantee backwards compatibility. As setforth earlier, late arrivals can always re-sync with the event.

Configuration Manager Component

FIG. 10 shows a flowchart delineating a technique for identifyingplayback devices of a plurality of client apparatuses which arenetworked to simultaneously playback an event. The present technique isimportant since the playback devices of the various client apparatusesmay differ in make and model. Thus, different commands are requiredtherefor.

In operation 1000, a type of the playback devices of the clientapparatuses is first identified. Such “type” may refer to a make, model,or any other distinguishing characteristic of the particular playbackdevices. A command associated with the identified type of the playbackdevice is then looked up in a look-up table. Note operation 1002. Suchtable may be located at the host server, or at any other location suchas the client apparatuses.

Thereafter, in operation 1004, the command is sent to the correspondingclient apparatus for beginning the playback of the event simultaneouslywith the playback of the event on each of the remaining clientapparatuses.

This component is thus responsible for identifying what type ofreference player is hosting the event. The reference player can be thedatabase, which contains the DVD commands or a real time player. Whenthe initial DVD is command is requested, the “Synchronizer” table isqueried for the host type. From that point forward, the scheduler wouldknow from whom to receive data.

DBConnect Component

This component is responsible for communicating with the Synchronizertables, and for providing access methods for the retrieved data. Allinteraction from the tables is on a read-only basis. The LayerImplcomponent communicates with this component to retrieve DVD commands andevent information.

Even though current implementation may be based on a Microsoft platform,hard dependencies on Microsoft or any other 3rd-party development toolsmay be avoided. To address such issues, the following considerations maybe made throughout the code:

MFC specific code may be avoided. Instead, STL may be used. ATL and/orMFC code may be encapsulated into separate classes and portioned fromthe rest of the code. Class implementations may use aggregation patternto delegate business logic to the portable classes. Database connectionclasses may be separated and the communication protocol may be separatedwith respect to portability to Oracle and other platforms.

FIGS. 11 and 12 illustrate the order of events among the variouscomponents of the present invention. In particular, FIG. 11 illustratesthe manner in which a layer factory is created. As shown, an event isfirst checked in a database server after which a business layer iscreated in a WEB server in a manner set forth hereinabove. The foregoingcomponents are then created. FIG. 12 illustrates the manner in whichuser requests are processed. As shown, communication is afforded withthe video player on the client machine by means of JAVAscript and JAVAapplets. The WEB server, in turn, communicates DVD commands to the videoplayer via the JAVA applets, and also interfaces the database server viathe various components thereof which were set forth hereinabove.

ALTERNATE EMBODIMENTS

To support future enhancements, further components may be included withextendibility as the major objective. Various future enhancements of theproduct and how they will be addressed will now be set forth.

Hosted Real Time Players

While spirals may retrieve pre-recorded DVD commands from the database,alternate spirals may support a consumer as a host. The architecture mayalso support plug-in components. Alternate spirals may support theRealTimeConnector component, which accepts host user request andforwards them to the clients. The instant architecture supports theDBConnector which accepts events from the database.

Keep Alive Connections

Clients may maintain connections throughout the event. This allows thehost to send a various number of commands to the client of the event.Although the spiral disconnects users once a PLAY command has beenissued, the Synchronizer class (which will be set forth later) adds eachconnection to a Thread Pool. This pool of connections can be left openduring the life of the event.

Logging Participants

Each request may be logged into the database to provide a reference forthe future.

DVD Positioning

As an option, connections may be pooled to allow the synchronizationserver to direct consumer's machines to the certain locations throughoutthe entire event.

Synchronization events in alternate spirals may be defined as acombination of play from location event and the actual event. This way,one describes each event in the unambiguous way on the client side andsynchronizes it with the server. For example, a situation may beconsidered where one fast forwards after a movie is played for 15 minand thereafter plays the scene in the movie. In such situation, one hasto submit the information to the client player, indicating that it(player) has to start time play from 15 min into the movie andfast-forward to the certain location. A better way would be to analyzewhat is the next event after fast forwarding occurred and perform acombination for the play from location and next event. This design wouldrequire significant changes to the client infrastructure, includingvideo object, remoteagent and provider and should be taken intoconsideration in any alternate client design.

Classes/Component Diagrams

FIGS. 13-16 illustrate various class/component diagrams. In particular,FIGS. 13-16 illustrate a Synchronizer Class Diagram 1300, LayerImplClass Diagram 1400, Business Layer Class Diagram 1500, and DBConnectClass Diagram 1600, respectively.

Sequence Diagrams

FIG. 17 illustrates a logical sequence diagram 1700. As shown, when theserver receives a user request, it analyzes the authenticationinformation of the request (date/time, disc id, user id, and BCA number)and the appropriate synchronization event stored in the database. Thedatabase contains an event start threshold value measured inmilliseconds. This threshold defines the amount of time prior to anevent that a consumer is eligible to “connect” for the start of theevent.

If the date/time of the user request lies within the event startthreshold, the user is put into wait queue and receive the appropriatedata when the time elapses. Note steps 1,2,3,5,6,7 of the LogicalSequence diagram. Otherwise, a message is sent informing the user whenthe event will occur. Note step 4 of the Logical Sequence diagram.

Server Side Collaboration Diagram

FIG. 18 illustrates a logical sequence diagram 1800 that shows serverside collaboration. As shown, server ISAPI extension receives aBroadcastVideoEvents request. It calls IA_BusinessServer viaBeginProcess, to retrieve configuration information. Configurationinformation contains a playback connector. Playback connector identifieswhether the server will have to communicate with a reference player orwill it perform playback from the database.

At step 6, ISAPI extension will call IA_BusinessServer CompareTimemethod and based on the results will send to the user a predefined webpage indicating to retry later or return control to the web server,notifying it (web server) to keep the connection open. At this pointconnection is pooled and will be processed by the IA_BusinessServer at atime of the event.

Client Collaboration Diagram

FIG. 19 illustrates a logical sequence diagram 1900 showing client sidecollaboration in accordance with one embodiment of the presentinvention.

Classes/Interfaces Definition

Definitions of one embodiment of the various classes associated with thesoftware which implements the present invention will now be set forth.

Class Applet1

Purpose:

This is the class that implements the applet. The browser will use it tobootstrap our applet.

Responsibilities:

-   -   Request a BroadCastVideo event and to gather event status        information.

Collaborations:

BroadCastEvent, CITIEncrypt

Base Class and Iplemented Interfaces:

Javax.Applet

Public Interface:

getChapter Returns the current chapter the reference player is playing.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getTitleInfo Returns the current title the reference player is playing

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getStartTime Returns the time the event is scheduled to start<SS:MM:HH:DD:MM:YYYY>

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getStartTimeSec Returns the time the event starts in seconds.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getStartTimeMinReturns the time the event starts in minutes.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getStartTimeHrReturns the time the event starts in Hours.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

GetStartTimeDay Returns the time the event starts in days.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

GetStartTimeMnth Returns the time the event starts in months.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

GetStartTimeYr Returns the time the event starts in year.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

GetLenOfEvent Returns the length of the event.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

-   -   GetExpiredTime: Returns lapse time of the event.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getServerTime: Returns the servers current time <SS:MM:HH:DD:MM:YYYY>.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getServerTimeSec: Returns the servers current in seconds.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getServerTimeMin: Returns the servers current in minutes.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getServerTimeHr: Returns the servers current in hours.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getServerTimeDay: Returns the servers current in day.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getServerTimeMnth: Returns the servers current in month.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

getServerTimeYr: Returns the servers current in year.

Return type: String Parameters: void Pre-conditions: None.Post-conditions: None.

startProc: Calls the ISAPIs “Serverinfo” method.

Return type: void Parameters: String disk id, String location idPre-conditions: None. Post-conditions: None.

msgEvent: Calls BroadCastEvent applet.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.Class BroadCastEvent

Purpose:

This is the class that invokes the Synchronizer.

Responsibilities:

-   -   Sets the JavaScript with the command returned from the server.

Collaborations:

CITIEncrypt

Base Class and Implemented Interfaces:

Java.Thread

Class CDBConnect

Purpose:

This is the class provides a public interface for components to requestinformation from the DB tables.

Responsibilities:

-   -   Opens the database and Synchronizer, Chapter_Disk tables.    -   Queries the Synchronizer by the specified disk id and location        id.    -   Queries the Chapter_Disk by disk id.    -   Provides the next chapter that is scheduled to play.    -   Queries the Decoder_Capabilities table to determine if the        requested player is time or chapter play.

Collaborations:

-   DBSyncSet-   DBReferenceSet-   CDBChapterSet-   CDecoderCapabilities

Base Class and Implemented Interfaces:

Public Interface:

Get_NextChapter: Returns the next chapter to play.

Return type: String Parameters: long time, long title, BSTR ChapterPre-conditions: None. Post-conditions: None.

chkEvent: Checks if an event is scheduled for the disk and location id.

Return type: String Parameters: long time, long title, BSTR ChapterPre-conditions: None. Post-conditions: None.

get_initialDVDCommand: Returns the first DVD command to play.

Return type: String Parameters: BSTR & Pre-conditions: None.Post-conditions: None.

get nextDVDCommand: Returns the next DVD command to play.

Return type: String Parameters: BSTR & Pre-conditions: None.Post-conditions: None.

decoderArray: Returns an array of decoder types.

Return type: String Parameters: long**, long** Pre-conditions: None.Post-conditions: None.Class CCConfigMgrImpl

Purpose:

This is the class provides a public interface for components todetermine the type of reference player hosting the event.

Responsibilities:

-   -   Opens the database and Synchronizer, Chapter_Disk tables.    -   Queries the Synchronizer by the specified disk id and location        id.    -   Stores the reference player type.

Collaborations:

CConfigMgrRecSet

Base Class and Implemented Interfaces:

Public Interface:

get_hostType: Returns the reference player host type.

Return type: String Parameters: short Pre-conditions: None.Post-conditions: None.Class ThreadFunctor

Purpose:

This class provides a threading model that classes can use to derive.

Responsibilities:

-   -   Calls the CreateEvent function, which opens a named or unnamed        event objec.    -   Calls _beginthread, which creates a thread begins execution of a        routine at start_address. The routine at start_address must use        the_cdecl calling convention and should have no return value.        When the thread returns from that routine, it is terminated        automatically.    -   Calls the WaitForSingleObject function, which checks the current        state of the specified object. If the object's state is        nonsignaled, the calling thread enters an efficient wait state.    -   Calls the ResetEvent function, which sets the state of the        specified event object to nonsignaled.    -   The state of an event object remains nonsignaled until it is        explicitly set to signaled by the SetEvent or PulseEvent        function.

Collaborations:

CConfigMgrRecSet

Base Class and Implemented Interfaces:

Public Interface:

start: Starts the thread.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.

stop: Stops the thread. Calls CloseHandle for the thread and event.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.Class Isapithread

Purpose:

This creates an ISAPI thread.

Responsibilities:

-   -   Adds a request to a vector.    -   Creates the sink object.    -   Stores the request into sink object.    -   Sends the time information to JavaScript.

Collaborations:

LayerSink

FactorySink

Base Class and Implemented Interfaces:

ThreadFunctor

Public interface:

addrequest: Adds the request to its vector.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.

getBLayerlnfo: Responsible for getting information about the event.

Return type: void Parameters: std:string&, std::string&,ChttpServerContext* Pre-conditions: None. Post-conditions: None.Class FactorySink

Purpose:

Manages the layerSink and businessLayerProp objects.

Responsibilities:

-   -   Stores a layerSink object.    -   Returns the “businesssLayerProp” <Business Layer Properties>    -   Creates the “businessLayerProp” <Business Layer structure>

Collaborations:

LayerSink

BusinessLayerProp

Base class and Implemented Interfaces:

Public Interface:

construct: Stores a layerSink object.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.

notifyCreateLayer: Responsible for creating a “businessLayerProp”.

Return type: void Parameters: BSTR, BSTR, DATE, DATE, LONGPre-conditions: None. Post-conditions: None.Class LayerSink

Purpose:

layerSink represents a sink interface and stores a queue of requests. Itcreates a connection point object.

This call back object, allows asynchronously processing.

Responsibilities:

-   -   Acts as the client sink object.    -   Sends the results to the user    -   Creates the “BusinessLayer” and makes it a connection point        object.    -   Closes the users connection.    -   Creates a Factory interface by calling “createFactory”.    -   Creates a connection point for the factory.    -   Stores the LayerSink in the FactorySink object.    -   Creates a connection point (call back) by calling AtlAdvise,        between the connection point container and the client sink        object. This allows the client to receive events.    -   Calls the connectable objects “getServerLayer”. This method        fires an event to the clients sink object.    -   Create a business layer,    -   Store the request in its vector.    -   Release the Sink Object (client)    -   Calls AtlUnadvise to terminates the ability of the client to        receive events.

Collaborations:

Base class and Implemented Interfaces:

Public Interface:

construct: Creates a connection point.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.

addRequest: Adds the request to its vector.

Return type: void Parameters: BSTR, BSTR, DATE, DATE, LONGPre-conditions: None. Post-conditions: None.

createBusinessLayer: Creates a business layer. Create the connectionpoint.

Return type: void Parameters: businessLayerProp & Pre-conditions: None.Post-conditions: None.

updatetime: This call back function translates the time and sends thecommand to the user.

Return type: void Parameters: long, long Pre-conditions: None.Post-conditions: None.Class CBusinessLayer

Purpose:

Creates a layerthread object. This object is responsible for providingaccess methods, which provide event information.

Responsibilities:

-   -   The “Synchronizers” createBusinessLayer method creates a class        object from the “IBusinessLayer” interface. <The class object is        part of the LayerImpl project>    -   The BusinesLayers class object <m_ilayer> calls its “Initialize”        method. <Note: m_ilayer is the connection point object. It        identifies the “Sink Interface”.    -   It then calls the “Initialize” method of the connection point.    -   The “Initialize” method then calls the “ChkValidEvent” method,        which then creates a layerthread object.

Collaborations:

CBusinessLayer

Layerthread

Base Class and Implemented Interfaces:

Public Interface:

Initialize: Calls the “ClikValidEvent” method which kicks of a layerthread.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.Class Layerthread

Purpose:

This object acts as a scheduler, processing request from its queue.

Responsibilities:

-   -   Send DVD commands to the user.    -   “Syncs” up late corners to the events.

Collaborations:

CBusinessLayer

CDBConnect

Base Class and Implemented Interfaces:

Public Interface:

startThread: Processes requests from the queue

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.Class CLayerFactory

Purpose:

This object manages businesslayer objects. Business layer objectscommunicate with the reference player and notify the user which DVDcommand to play.

Responsibilities:

-   -   Send DVD commands to the user.    -   “Syncs” up late corners to the events.    -   This object Implements the IID_LayerFactory interface.    -   This COM object is the servers Connectable Point object.    -   This server object supports connections to sink interfaces.        These sink interfaces reside on the client side and are        equivalent to the “call back” functions in Windows.

Collaborations:

CBusinessLayer

CDBConnect

Base Class and Implemented Interfaces:

Public Interface:

getServerLayer: “Fires” an event to create a business layer with theproperties retrieved from the pipe object.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.

put_set_layer: call the “CLayerFactoryhnpl” add( ) method. Supplying the“businesslayer” object.

This will added to shared memory queue and written to a file.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.

FinalConstruct: Calls the “CLayerFactoryImpl” FinalConstruct COM classobject.

Return type: void Parameters: void Pre-conditions: None.Post-conditions: None.Remote Control of Local Content:

With reference to FIG. 20, the present invention provides a system andmethod for remote control of local content which enables the control ofVideo Playback from a remote server. Content stored on a medium 2002such as a DVD is loaded onto a client device 2004. This hardware can be,for example, a computer, set top device such as is used to access WebTV,or some other device. The hardware device 2004 of the present embodimenthas software 2006 in the form of a browser or presentation engine. Inaddition, the hardware 2004 has DVD Firmware or a Navigator 2008 incommunication with the browser/presentation software 2006.

With continued reference to FIG. 20, a server 2010 delivers content tothe hardware 2004 to be used in conjunction with the DVD 2002. Thiscontent can be in the form of ROM/HTML Content 2012 and/or DVD-VideoContent 2014. Depending on the desired application, this content 2012and 2014 enhances and/or allows a DVD experience 2016 provided by theDVD medium 2002.

With reference to FIG. 21, this control is performed by a transactionsever 2102 which sends video playback commands 2104 such as play stop,FF, Rewind, etc. It can also provide a locking/unlocking scheme whichallows content on a local disk 2106 or website to be protected andaccessible to particular users at prescribed points in time through alocking and unlocking process. This locking/unlocking technology couldbe broken down into two possible embodiments. For example, one suchembodiment allows for unlocking local content that is on a local disk(i.e. DVD Disc) 2106 based on a user profile for example. In additionthis content access could also expire or be accessible only during aparticular time frame. Another possible embodiment allows for unlockingcontent on a website 2108 by requiring the user to have a DVD Disc inhis computer's disc drive or set top box. (Therefore the user had topurchase the disk to get access to the on-line content).

This locking and unlocking is accomplished through the transactionserver 2102, which validates the credentials of the user. Thesecredentials 2110 are passed from the client 2112 (PC or set top box) andthe server returns for example the unlock sequence 2114 to the client.In the case of DVD Video this unlock sequence can be in the form ofGeneral Purpose Registers Values (GPRM Bits) that unlock the content. Inthe case of the website the client 2112 could pass the current disc 2106in the drive's unique disc ID or BCA number and the transaction server2102 allows a redirection to protected content after validation takesplace. This unlocked content could be local or on the website 2108.

The advantages of remote control of a client's video device from aserver is that the content can be protected. Since the information touse it is stored remotely, it can be easily maintained and upgraded, andallows introduction of new products without affecting the alreadyshipped content (DVD Video). In addition, the control can be of a singleclient or many users. For example, with the ability to unlock contentyou can allow content to be accessible at a particular point in timethus allowing a special “event” or promotional time to occur and alsoallowing for various advertising/promotional models. The concept ofexpiring content is also useful, for example if an offer is only validtill the end of the year. The user is not burdened with viewingadvertising or offers that they cannot participate in anyway after theyhave expired.

Another example is to reward users for purchasing particular products oreven registering their products. The user can then be provided withadditional content that is unlocked on the disc. In addition we canverify that people have the correct credentials before accessingcontent. To explain this further there may be website material thatshould only be accessible to customers who have purchased a particularDVD. The website may have additional information, games, or specialitems to be purchased and offered and this should only be made availableto people who have purchased the DVD product. This may also span acrossmultiple products for example if a user has purchased all of theavailable Lethal Weapon TM titles it may be desirable to give additionalcontent to that user for having purchased the series. Another embodimentof the invention follows the DIVX DVD model wherein a client is chargedon a per usage basis for the content.

The present invention can also provide for remote navigation of contenton a local server. For example navigation commands 2104 (FIG. 21) forleft, right, up, down can be sent from the server to set General PurposeRegisters (GPRMs) in the DVD Player that allowed content to be unlockedand viewed by users during the event. In addition, DVD navigationcommands can be sent through streamed audio with embedded triggers thatsend DVD navigation commands that call the video object in the web page.

In addition, With reference to FIG. 22, a synchronization server 2202can be used to send commands to initiate video play in synchronizationwith several users 2112. Control can be of one or multiple clients inthe form of PCs 2204 or set top players 2206. The remote navigationcommands 2208 allow the server to tell the client what to do. The sameset of commands can be sent to each of the clients—thus synchronizingthe viewing experience. They could also be different, for example eachuser could be viewing a different DVD and therefore experiencing adifferent set of content. Based on the users profile 2210 they can alsohave access to different content. Given a geographical location ornative language the control maybe tailored accordingly. The control ofthe video can be as simple as play, stop, fast forward, rewind, etc. orcan include advanced features such as pan, zoom, rotate etc. The type ofnavigation/control can be divided into 3 aspects:

-   -   Commands. Commands control the playback and search mechanisms of        a DVD-Video disc. (These can be issued from the server or the        client)    -   Properties. Properties are used to query attributes of the        DVD-Video and set certain configuration properties. (These can        be queried from the server or the client). An example is to get        the current state or title/chapter/time of the DVD Video).        Another example is to tell the user whether or not he or she is        on a menu.    -   Events. Events are used to trigger notification of various        playback conditions, such as time changes, title changes and UOP        changes. Events are essential for scripting and synchronizing        the video with other assets, (these are sent from the content or        client back to the server. They can indicate that the video has        stopped playing, you are on a menu item, or the number to angles        available in the video has changed.

Embodiment in a Web Page

With reference to FIG. 23, an embodiment of this invention providescontrol of content through a web page 2302. Using a browser as theclient interface (Such as Internet Explorer) the user can browse to thepage 2302 on-line that contains an Active-X Control that has an embeddedvideo object 2304. The client sends identification information and/orrequests 2305 to the web page over the Internet 2306. In response, thevideo object 2304 activates video navigation commands to play and/orunlock sequences 2308 required to play the video.

With reference to FIG. 24, in another embodiment of the invention theVideo Object 2304 opens a secondary connection 2402 to the transactionserver 2102 to receive commands 2404 from the server to execute.

In another form the browser interprets http commands for the control ofvideo. The web page on the server is viewed by the client and when theuser selects an item in the web page the HTTP link can be formatted withparameters for the browser to interpret directly for video playback.

For example http://iti_video? command=Play

This is interpreted by the browser since it has an iti_video in the urland then parses the parameters, which in this case is the command toplay.

EXAMPLES OF EMBEDDING A VIDEO OBJECT IN A WEB PAGE

DVD-Video can be embedded within a HTML page and control its layout.Computer operating systems can embed DVD-Video using currently availableembedding techniques. By way of example, each of the major computeroperating systems is provided below:

Operating System Example Windows <object ID=“ Video Object”  CLASSID=“clsid: A0739DE5-571F-11D2-A031- 0060977F760C”   BORDER=“1”WIDTH=50% HEIGHT =60%> </object> Apple/Macintosh <embed ID=” VideoObject”   TYPE=”application/x- Video Object -plugin”   ALT=”Video ObjectPlug In”   HIDDEN=”TRUE”> </embed> Linux TBD Others TBD

After the DVD-Video object is embedded in the web page, it can beaccessed using any style sheet, link, or scripting language. Values forthe IDstring must begin with a letter (A-Z or a-z) and may be followedby any number of letters, digits, hyphens, and periods up to a maximumof 48.

Unlike computers, set-top boxes do not generally have a full-blownoperating system and browser. Therefore, the capabilities within thebrowser are often more restricted. For embedding DVD-Video within theseplatforms using ITX, the “Video Object” ID must be integrated within theembedded browser as any other tag structure. With this approach, anyembedded browser that encounters the “Video Object” tag, wouldautomatically associate this identifier.

Unlocking Implementation:

Another embodiment of the invention provides a system and method forunlocking portions of DVD-Video based on certain criteria (date,profile, BCA, etc.). To control playback of video, the video can be“locked” so that the consumer must perform certain steps to access andplay the video. The steps that trigger the unlock should be controlledby the content owner and can be based on date, consumer profile, BCAnumber or any other criteria, and should be controllable over theInternet from a remote server. (Although it is possible to store theunlock sequence locally as well). With reference to FIG. 25, a method2502 is provided for controlling content. The method 2502 begins with astep 2504 wherein a user tries to play a portion of DVD-Video fromapplication or web page. In a step 2506, video software initiates asecure connection to a transaction server that authenticates the user,and then passes the correct unlock sequence of events back to the videosoftware. This video software is preferably stored locally on the user'scomputer or, more preferably, on the disk on which the video content isstored. In a step 2508, the events are passed from the server, and thenin a step 2510 are then passed by the video software directly to theunderlying hardware or software DVD decoder, thereby bypassing any userknowledge of the events. This approach requires certain DVD-Videoauthoring requirements: (1) interleaving video and audio streams toprevent “back door” playback/access; (2) ability to populate GPRMs tocreate locking sequence.

There are two parts to the DVD-Video unlocking mechanism:

-   -   The actual unlock process—performs actual unlocking of video.        Without unlock process, consumer cannot access video. Therefore        software on the remote server is required to unlock the video        and other players will not support this feature.    -   The protection process—the process protects against malicious        consumers who try to bypass unlocking process. This process is        not an actual locking process, but manipulates and distorts the        video, thus rendering it non-viewable by consumers that try to        bypass the unlock mechanism.        Unlock Process

The locking process is performed during the video authoring process ofthe DVD-Video. Each portion of video to be unlocked can be authored intoa separate title, or title/chapter combination. (All references tolocking video also apply to locking DVD-Audio)

The locking of the video utilizes General Parameter Registers (GPRMs),which are inherent in the DVD-Video specification. A DVD-Video title canbe authored such that the GPRMs must be set to a specific value in orderto allow an action to occur. In the case of our video unlocking scheme,the process of locking a video is ensuring that a video can only beplayed when the GPRMs are properly set. Then the DVD-Video is authoredin such a way that remote server operator can programmatically (withoutconsumer interaction) set the value of the GPRMs when certainconditions/transaction criteria has been met.

FIG. 26 illustrates a method 2602 for unlocking content. The stepsrequired to create the “lock” or “key” for unlocking begin with a step2604 of creating a title, the title being some form of content such as amovie video, training video or some other form of content. Thereafter,in a step 2606 hot spots are authored in the title (or use post commandand jump to menu that contains hot spots). Then, in a step 2608, all ofthe hotspots are overlapped. In a step 2610 a sequence of events thattrigger GPRMs is passed to the client. Once correct sequence of eventsare passed to client, resulting in populating the GPRMs properly, then,in a step 2612 the consumer is allowed to play the locked video.

Once correct GPRMs are populated, the appropriate post command isgenerated to jump the consumer to the locked title. Also note the GPRMscan be populated by either a direct call to an interface that allowssetting the GPRM bits or through menu navigation commands such as left,right, up, and down.

It is also recommended to create a TIFF or animated graphic thatdisplays when the DVD is placed into a traditional DVD consumer player.This TIFF or animated graphic can inform the user to place the DVD intoa computer to access the special features and unlock the appropriatecontent. This information is displayed as soon as the First Play PGC isencountered.

Protection Process:

To avoid DVD playback solutions that violate the DVD-Video guidelines,additional precautions should be taken (these are not required, butrecommended):

Referring next to FIG. 27, shown is a flowchart illustrating oneembodiment of steps carried out by a server when remotely unlockinglocal content. Initially, the server, e.g., transaction server 2102 ,receives device identification data from a client device, e.g., client2112 (PC or set top box)(Step 2750). The identification data in someembodiments is associated with information in the Burst Cut area of alocal disk, e.g., local disk 2106. Next, the server authenticates theidentification data at the server to determine whether the client deviceshould have access to the locked content (Step 2752). In response toauthenticating the identification data, the server sends to the clientdevice unlocking data for setting a register in the client device andallowing the client device access to the locked content (Step 2754). Inseveral embodiments, the locked content has been authored such that whenthe register is set to a specific value a post command is generated inthe client device that directs the client device to the locked content(Step 2756).

-   -   Each section of video (title or chapter) to be locked should be        interleaved with another portion of video (such as black, or        with a second video to be locked. Since this requires the use of        multi-angle content, the two sections of video must be of the        exact length. This avoids certain decoders which ignore the        DVD-Video layout and allow the consumer to play a VOB file        directly. The first/default video stream (angle 1) should be the        black, dummy video. The second video stream (angle 2) should be        the actual content to be unlocked.    -   Each section of video to be locked should contain two audio        tracks: the first/default audio track should be noise, garbage        or any audio that is NOT associated with the content to be        unlocked. This is the default audio track that will be played if        the consumer attempts to bypass the DVD-Video specification. The        second audio track should be the actual audio track for the        locked video.

This protection process is useful because interlaced/multi-angle videois formatted out sequentially. In other words, interlaced content isstored in the following manner: Seconds 0-2 video 1, seconds 0-2 video2, seconds 3-5 video 1, seconds 3-5 video 2, etc. Therefore if aconsumer attempts to play the underlying VOB file directly, they willsee video alternating every two seconds—which is very annoying.Additionally, if a VOB file is played using this approach, the defaultaudio stream will play, which as defined above, will be garbage.

If utilizing these protection processes: after unlock process hascompleted successfully, the DVD-Video should be authored to play theappropriate title/chapter combination, as well as defaulting to thesecond video stream (angle 2) and second audio stream (audio track 2).Relate to BCA based on distribution channel allow access to content.

Control is on the Server side and it controls the client. Thereforeserver can give commands for content. The server can also create a gameout of the navigation if they view certain clips in a certain order theywill essentially be walking through a key setting scheme and thusunlocking further content. The Unlock information on a web site byrequiring a DVD to be in the drive. The BCA number or Disk ID is passedto the website in the HTTP header and then this allows the content onthe website to be accessed.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any other the above described exemplary embodiments,but should be defined only in accordance with the following claims andtheir equivalents.

1. A method for remotely controlling content at a client devicecomprising the steps of: receiving credentials from the client device ata server; authenticating the credentials at the server; and sending, inresponse to the authenticating, an unlock sequence to the client device,wherein the unlock sequence triggers the client device to locate thecontent for playback at the client device.
 2. The method of claim 1,wherein the step of receiving credentials comprises receivingcredentials from a burst cut area of a removable medium, wherein thecontent is located on the removable medium.
 3. The method of claim 1wherein the step of sending comprises sending the unlock sequence to theclient device, wherein the unlock sequence is a function of thecredentials, thereby triggering the client device to locate particularcontent as a function of the credentials.
 4. The method of claim 1further comprising: comparing a date the credentials are received with avalid time period for the content; wherein the step of sending is inresponse to both the step of authenticating rendering an authenticationand the step of comparing indicating that the date is within a validtime period for the content.
 5. The method of claim 1, wherein the stepof sending comprises sending the unlock sequence to the client devicewherein the client device comprises a Digital Versatile Disc (DVD)player that operates according to a DVD-Video Specification, wherein thecontent is stored on a Digital Versatile Disk (DVD).
 6. The method ofclaim 5 wherein the step of sending the unlock sequence comprisessending navigation commands that set a general parameter register at theDVD player to a particular value in response to the authenticating,wherein the general parameter register is inherent in the DVD-Videospecification, wherein the content has been authored such that when thegeneral parameter register is set to the particular value, a postcommand is generated in the client device that directs the client deviceto the content.
 7. A computer readable medium encoded with code segmentsfor controlling content remotely, the computer readable mediumcomprising: a code segment for receiving credentials from the clientdevice at a server; a code segment for authenticating the credentials atthe server; and a code segment for sending, in response to theauthenticating, an unlock sequence to the client device, wherein theunlock sequence triggers the client device to locate the content forplayback at the client device.
 8. The computer readable medium of claim7, wherein the code segment for receiving credentials comprises a codesegment for receiving credentials from a burst cut area of a removablemedium, wherein the content is located on the removable medium.
 9. Thecomputer readable medium of claim 7, wherein the code segment forreceiving credentials comprises a code segment for receiving credentialsfrom a burst cut area of a removable medium, wherein the content islocated on the removable medium.
 10. The computer readable medium ofclaim 7, wherein the code segment for sending comprises a code segmentfor sending the unlock sequence to the client device, wherein the unlocksequence is a function of the credentials, thereby triggering the clientdevice to locate particular content as a function of the credentials.11. The computer readable medium of claim 7 further comprising: a codesegment for comparing a date the credentials are received with a validtime period for the content; wherein the code segment for sendingcomprises a code segment for sending the unlock sequence in response toboth the code segment for authenticating rendering an authentication andthe code segment for comparing indicating that the date is within avalid time period for the content.
 12. The computer readable medium ofclaim 7, wherein the code segment for sending comprises a code segmentfor sending the unlock sequence to the client device wherein the clientdevice comprises a Digital Versatile Disc (DVD) player that operatesaccording to a DVD-Video Specification, wherein the content is stored ona Digital Versatile Disk (DVD).
 13. The computer readable medium ofclaim 12, wherein the code segment for sending the unlock sequencecomprises a code segment for sending navigation commands that set ageneral parameter register at the DVD player to a particular value inresponse to the code segment for authenticating rendering anauthentication, wherein the general parameter register is inherent inthe DVD-Video specification, wherein the content has been authored suchthat when the general parameter register is set to the particular valuea post command is generated in the client device that directs the clientdevice to the content.
 14. A method for accessing local content at aclient device; sending credentials from the client device to a remoteserver; receiving, in response to the credentials being authenticated atthe remote server, an unlock sequence; locating the content in responseto receiving the unlock sequence; and accessing the content.
 15. Themethod of claim 14, wherein the step of sending credentials comprisessending credentials from a burst cut area of a removable medium, whereinthe content is located on the removable medium.
 16. The method of claim14 wherein the step of receiving the unlock sequence comprises receivingvalues for general parameter registers; wherein the step of locatingcomprises generating a post command to direct the client to the content.17. The method of claim 14 wherein the step of locating the contentcomprises locating a particular portion of the content as a function ofthe unlock sequence, wherein the unlock sequence is a function of thecredentials.
 18. The method of claim 14 further comprising the step of:comparing a date the credentials are received with a valid time periodfor the content; wherein the step of sending is in response to both thestep of authenticating rendering authentication and the step ofcomparing indicating that the date is within a valid time period for thecontent.
 19. The method of claim 14, wherein the code segment forsending credentials comprises a code segment for sending credentialsfrom a burst cut area of a removable medium, wherein the content islocated on the removable medium.
 20. The method of claim 14 wherein thecode segment for receiving the unlock sequence comprises a code segmentfor receiving values for general parameter registers; wherein the codesegment for locating comprises a code segment for generating a postcommand to direct the client to the content.
 21. The method of claim 14wherein the code segment for locating the content comprises a codesegment for locating a particular portion of the content as a functionof the unlock sequence, wherein the unlock sequence is a function of thecredentials.
 22. A computer readable medium encoded with code segmentsfor accessing local content at a client device, the computer readablemedium comprising: a code segment for sending credentials from theclient device to a remote server; a code segment for receiving, inresponse to the credentials being authenticated at the remote server, anunlock sequence; a code segment for locating the content in response toreceiving the unlock sequence; and a code segment for accessing thecontent.